International one-way recorded transmitter over a cellular network

ABSTRACT

Agencies oftentimes desire to monitor personnel in the field during the course of their duties. To provide flexible monitoring capabilities to agencies, a common mobile device such as a mobile phone is converted for use as a radio-based listening system to collect and transmit audio data. A relay is implemented within the system to pass message communications between the mobile device and a server such that the server can facilitate establishment of sessions for monitoring the mobile device.

CROSS REFERENCE TO RELATED APPLICATIONS

This a continuation of U.S. application Ser. No. 15/099,499, filed Apr.14, 2106 which claims the benefit of U.S. Provisional Application No.62/148,001, filed Apr. 15, 2015, which is incorporated by referenceherein in its entirety.

BACKGROUND 1. Field of Art

The present disclosure generally relates to the field of undercoveroperations and more specifically to using a mobile phone as anundercover device.

2. Background of the Invention

Police officers and other agents “operators” oftentimes conductinvestigations in the field during the course of their duties. In manycases, these investigations require direct support and oversight at anadministrative level. For example, an operator conducting an undercoversting in a high-risk situation may have a support team monitoring theoperator directly in the field and interfacing with administration at anagency. Traditionally, the operator would use a radio-based covertlistening system that can be hidden (e.g., under a shirt) or otherwiseembedded (e.g., in or on an electronic device or object) to conceal itsnature and protect operators' cover. The listening device would thentransmit audio data back to the support team, which would relay databack to the agency.

However, with widespread publicity of listening devices in movies andthe like, the physical nature of a given device can lead to itsdiscovery or detection, which poses additional risks for the operatorsthemselves. Additionally, traditional bugs have other inherentdeficiencies when used in the field, such as requiring line-of-sight orphysical proximity to a base station and the support team. Although somenewer bug systems seek to provide sufficient concealability among otherdesirable features, they are oftentimes prohibitively expensive and yet,still fail to mitigate the above deficiencies. Furthermore, such systemsare not rapidly deployable as they typically require support personnelother than immediate backup.

SUMMARY

The above and other issues are addressed by a method and computer systemfor configuring a telephonic device as a one-way recorded transmitter(mobile bug). An embodiment of the method comprises receiving a requestfor a virtual number from an intermediate telephonic device (relay). Inresponse to the request for the virtual number, the virtual number isprovisioned and a PIN is generated. The PIN is associated with thevirtual number and transmitted to the relay. A registration request forthe mobile bug is received from the relay and includes the PIN anddevice information, such as a transmitting number, for the mobile bug.The virtual number is identified based on the PIN. Responsive toidentifying the virtual number based on the PIN, the received deviceinformation for the mobile bug is stored in association with the virtualnumber. An activation request for the mobile bug is received from therelay. In response to the activation request for the mobile bug, themethod further includes transmitting instructions for connecting themobile bug to the virtual number to permit monitoring of the mobile bug.Outgoing audio to the mobile bug is disabled. In an embodiment, theactivation request includes the PIN and/or the device information forthe mobile bug associated with the virtual number. In turn, the virtualnumber is identified based on the received PIN and/or the receiveddevice information included in the activation request.

In an embodiment, the relay and the mobile bug are associated with afirst telephony network and the virtual number is provisioned with asecond telephony network, the instructions for connecting the mobile bugto the virtual number comprising instructions to dial out to the mobilebug from the virtual number to establish a connection through thevirtual number.

In some embodiments, the method further comprises configuring a secondtelephonic device as a monitoring device. A registration request for themonitoring device is received from the relay and includes deviceinformation, such as a transmitting number, for the monitoring device.The registration request for the monitoring device may include a secondPIN, different from the first PIN, to distinguish the registrationrequest for the mobile bug from the registration request for themonitoring device. In an embodiment, the second PIN for monitoring isgenerated, associated with the virtual number, and transmitted to therelay. The virtual number is identified based on the second PIN.Responsive to identifying the virtual number based on the PIN, thereceived device information for the monitoring device is stored inassociation with the virtual number. The method further comprisestransmitting, in response to receiving the activation request for themobile bug, instructions for connecting the monitoring device to thevirtual number to receive audio transmitted by the mobile bug. In anembodiment, the instructions for connecting the monitoring device to thevirtual number comprise instructions to dial out to the monitoringdevice from the virtual number to establish a second connection throughthe virtual number. The audio is transmitted by the mobile bug over thefirst connection established through the virtual number and themonitoring device receives the audio on the second connectionestablished through the virtual number.

An embodiment of the system comprises a server having a one or moreprocessors and a non-transitory computer-readable storage medium storingcomputer program code. When executed, the computer program code causesthe server to receive a request for a virtual number from anintermediate telephonic device (relay). In response to the request forthe virtual number, the server provisions the virtual number andgenerates a PIN. The PIN is associated with the virtual number andtransmitted to the relay. A registration request for the mobile bug isreceived from the relay and includes the PIN and device information,such as a transmitting number, for the mobile bug. The virtual number isidentified based on the PIN. In response to identifying the virtualnumber based on the PIN, the received device information for the mobilebug is stored in association with the virtual number. An activationrequest for the mobile bug is received from the relay. In response tothe activation request for the mobile bug, the server further includescomputer program code to transmit instructions for connecting the mobilebug to the virtual number to permit monitoring of the mobile bug.Outgoing audio to the mobile bug is disabled. In an embodiment, theactivation request includes the PIN and/or the device information forthe mobile bug associated with the virtual number. In turn, the serveridentifies the virtual number based on the received PIN and/or thereceived device information included in the activation request.

In an embodiment, the relay and the mobile bug are associated with afirst telephony network and the virtual number is provisioned with asecond telephony network, the instructions for connecting the mobile bugto the virtual number comprising instructions to dial out to the mobilebug from the virtual number to establish a connection through thevirtual number.

In some embodiments, the server further comprises computer program codeto configure a second telephonic device as a monitoring device. Aregistration request for the monitoring device is received from therelay and includes device information, such as a transmitting number,for the monitoring device. The registration request for the monitoringdevice may include a second PIN, different from the first PIN, todistinguish the registration request for the mobile bug from theregistration request for the monitoring device. In an embodiment, thesecond PIN for monitoring is generated, associated with the virtualnumber, and transmitted to the relay. The virtual number is identifiedbased on the second PIN. In response to identifying the virtual numberbased on the PIN, the received device information for the monitoringdevice is stored in association with the virtual number. The serverfurther comprises computer program code to transmit, in response toreceiving the activation request for the mobile bug, instructions forconnecting the monitoring device to the virtual number to receive audiotransmitted by the mobile bug. In an embodiment, the instructions forconnecting the monitoring device to the virtual number compriseinstructions to dial out to the monitoring device from the virtualnumber to establish a second connection, the monitoring device receivingaudio on the second connection from the first connection establishedthrough the virtual number with the mobile bug.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the embodiments can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings.

FIGS. 1A and 1B are block diagrams illustrating an environment forimplementing a system for a mobile phone as a one-way recordedtransmitter “mobile bug” activated through a relay according to exampleembodiments.

FIG. 1C is a block diagram illustrating an operating environment of amobile bug activated through a relay according to an example embodiment.

FIG. 2 is a block diagram illustrating a bug module according to oneexample embodiment.

FIG. 3A is an interaction diagram illustrating a method for requesting avirtual number and registering a mobile bug and/or monitoring devicewith the virtual number through a relay, according to exampleembodiments.

FIG. 3B is an interaction diagram illustrating a method for provisioningand mapping virtual numbers for operating and monitoring a mobile bugaccording to one example embodiment.

FIGS. 3C and 3D are tables illustrating example embodiments of virtualnumber mapping for operating and monitoring a mobile bug.

FIG. 4A is an interaction diagram illustrating a method for activating amobile bug through a relay according to one example embodiment.

FIG. 4B is an interaction diagram illustrating a method for monitoring amobile bug with a monitoring device according to one example embodiment.

FIG. 5 is an interaction diagram illustrating a method for operating amobile bug according to one example embodiment.

FIG. 6 is an interaction diagram illustrating a method for monitoring amobile bug according to one example embodiment.

DETAILED DESCRIPTION

The Figures (FIG.) and the following description relate to preferredembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesof the embodiments.

Reference will now be made in detail to several embodiments, examples ofwhich are illustrated in the accompanying figures. It is noted thatwherever practicable, similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments for purposes of illustration only.

OVERVIEW

Many operators in the field posses a personal mobile phone or are issueda mobile phone by their agency or department. Oftentimes a traditionalbug and accompanying support team are unavailable to support an operatorin the field or are not appropriate for a given scenario. However, theagency may still desire to monitor and/or record the operator'sactivities. Accordingly, the agency may coordinate with an agencysupport service to provide configuration of the operator's mobile phoneto fulfill the role of a traditional bug. The configuration can takeplace over-the-air such that a given mobile phone is convenientlyconverted as needed. In some instances, the mobile phone requiresnothing more than a radio connection. If the agency desires to monitoradditional operators, additional mobile phones may be converted.Monitoring devices, embodiments of which may also be mobile phones, mayalso be configured to monitor the mobile phone of the operator. As such,agency personnel in the field may monitor activities of the operatorwhen the operator's mobile phone is activated through the agencyservice.

Example embodiments described herein relate to configuring a wirelessradio network (e.g., Cellular Network and/or WiFi) capable device, suchas a mobile phone, as a one-way recorded transmitter or “mobile bug” foruse in the field. As mobile phones and similar devices are commonlycarried by operators during the course of undercover investigations,mobile phones offer an existing platform for transmitting datawirelessly. Use of such devices as a mobile bug often allows the mobilebug to be concealed “in plain sight” as a direct result of the devices'popularity and utility. Additionally, with the popularity of smartphones and feature phones, additional monitoring and safety features areintegrated into the mobile bug for enhancing operational viability inthe field.

Furthermore, because a mobile phone configured as a mobile bugcommunicates information over existing channels created for the phone'sintended purpose, the mobile bug, if examined, at worst appears tooperate as expected (e.g., receives and/or transmits wireless data).Accordingly, the worst case scenario for an operator is having to“turn-off” the mobile bug rather than having their cover blown.Additionally, by turning a mobile phone into a covert transmittingdevice and using a cellular network as the means of transmission, themobile bug system offers a virtually unlimited range of transmission andthe ability to collect a wide range of valuable real-time data.Real-time data collected by the mobile bug may include audio, video orstill images, Global Positioning System (“GPS”) coordinates, etc.

The mobile bug subsequently transmits all or a portion of the collectedreal-time data wirelessly over the existing channels (e.g., a network)back to the agency, agency service or another entity. Embodiments of theagency, agency service and/or other entities within the mobile bugsystem receive the collected data for storage and/or live streaming tomonitoring devices. Depending on the embodiment, the monitoring devicesare further configured to access and present (e.g., play and/or display)a variety of the real-time and historical data stored on or streamed bythe entities on the network. For example, the monitoring devices mayaccess a web interface, API or execute a standalone application forviewing mobile bug details and the collected information. In someembodiments, the monitoring devices may access portions of the real-timedata via a provided monitoring line configured for maintaining theoperator's cover. Furthermore, other agencies with appropriatecredentials and monitoring devices may similarly access portions of thecollected information during inter-agency investigations.

Environment and Implementation of the Mobile Bug System

FIG. 1A is a block diagram illustrating an environment 100 a forimplementing a system for a mobile phone as a one-way recordedtransmitter “mobile bug” activated through a relay according to anexample embodiment. As shown the environment 100 a includes networkssuch as telephony network 125A, telephony network 125B, and internet123.

Most, if not all, countries include communication infrastructure such asa telephony networks 125 and internet 123. However, the sophisticationand interoperability between the networks of different countries maydiffer greatly. For example, while inbound and outbound calls may becompleted between telephony network 125A and telephony network 125B,other well known communication types such as messages, e.g., on a shortmessage service (SMS) and multimedia message service (MMS), thoughsupported within the networks separately, may not be completed betweenthe networks. As an example, a message originating from a device onnetwork 125A may not be received by a device on network 125B and viceversa. In another example, telephony network 125B may support virtualnumbers 101 and telephony network 125A may not. Additionally, ininstances where caller ID information is used by the agency service 115to distinguish between different telephonic devices dialing a virtualnumber, a telephony network (e.g., 125A) may be unable to pass reliablecaller ID information to the agency service (regardless of which networkthe virtual number is associated with) for the telephonic devices. Assuch, additional information input from the user of a telephonic devicedialing the virtual number may be required for the agency service 115 toidentify the device, even if telephony network 125A supports virtualnumbers. These shortcoming present difficulties for personnel in thefield and/or configuration of telephonic devices as mobile bugs and/ormonitoring devices.

In order to mitigate the above shortcomings, a relay 113 is coupled tothe telephony network 125A for supporting the configuration of mobilebugs and monitoring devices on the telephony network 125A. The relay 113passes information and instructions received from devices coupled to thetelephony network 125A to the agency service 115 and vice versa. Exampleembodiments of the relay 113 can include telephonic devices withconnectivity to the internet 123 and the telephony network 125A. Thecoupling to telephony network 125A supports communication with othertelephonic devices coupled to the telephony network 125A. The couplingto internet 123 support communication with the agency service 115.Accordingly, the relay 113 facilitates communications between telephonicdevice on the telephony network 125A and the agency service 115. Forease of deployment, the relay 113 may be a mobile phone or other mobiledevice capable of receiving and transmitting messages on services suchas SMS and MMS over telephony network 125A and capable of internet 123connectivity to communicate with the agency service 115. In anembodiment, the relay 113 passes messages received on the telephonynetwork 125A to the agency service 115 via the internet 123.Additionally, the relay 113 may receive messages for transmission fromthe agency service 115 via the internet 123 and, in turn, transmit themessages on the telephony network 125A. Thus, generally, the relay 113can be embodied as any device with connectivity to the agency service115 and that the mobile bug 105 and monitoring device 107A can send andreceive messages with (e.g, over a telephony network 125A and/or theinternet 123)

For example, in some embodiments, the relay 113 may be implemented as abot on a server, such as an Internet bot, web robot, WWW robot or simplybot. A bot implemented on a server may be a software application thatautomated tasks over the Internet. For example, a bot configured as arelay 113 includes the ability to send and receive messages to and fromdevices such as mobile bugs 105 and monitoring devices 107 and transmitthose messages over the Internet to the agency service 123. In oneembodiment, a bot configured as a relay 113 may be implemented withinpopular over-the-top messaging (OTT) applications such as TELGRAM,WHATSAPP, FACEBOOK MESSENGER, or other messaging application. Bots, likeusers, are traditionally addressable over these networks by usernames,such as “@RelayBot.” As bots are implemented virtually as softwareapplications, a bot configured as a relay 133 may remove the need for aphysical relay 113 device coupled to a telephony network 125A, providingthe devices 105, 107A include connectivity to the internet 123 throughtheir telephony network 125A. Accordingly, where these conditions aremet, a bot configured as a relay 113 may enable instant globaldeployment of a mobile bug 105 without requiring configuration of aphysical relay device coupled to telephony network 125A. In the contextof the system described herein, a device used as the mobile bug 105and/or monitoring device may launch an OTT application such as TELEGRAM,compose a new message within the OTT application and transmit themessage to the user name (e.g., “@RelayBot”) of the bot configured as arelay to perform actions in a manner similar to that of transmitting themessage over SMS. Similarly, the device may receive a response back fromthe bot configured as the relay, but within the OTT application ratherthan via SMS. The bot configured as the relay 113 may transmit themessages received from the mobile bug 105 and/or monitoring device 107Aback to the agency service 115 (e.g., over the internet 123, eitheroutside or within the OTT messaging application) and receiveinstructions for transmitting messages to the mobile bug 105 and/ormonitoring device 107A back from the agency service 115. As can be seen,the relay 113 may be implemented in a variety of way to overcomedifficulties that arise in supporting mobile bugs 105 and/or monitoringdevice 107 operations abroad.

The agency service 115 is coupled to the internet 123 and the telephonynetwork 125B. One or more mobile bugs 105 and monitoring devices 107Amay be coupled to the telephony network 125A, and are configured throughthe relay 113. Monitoring devices 107 and mobile bugs 105 may alsoconnect to the internet 123, and other monitoring devices (not shown)may also be coupled to the telephony network 125B. For example,monitoring device 107B as shown is coupled to the internet 123. Anagency (not shown) may communicate with the agency service 115 (e.g.,via the internet 123 or other network) to retrieve information relativeto operations conducted with the mobile bug 105. For example, the agencymay retrieve recordings and other data collected by the mobile bug 105.

Agency service 115 represents a collection of compute devices (e.g.,servers) and related storage mediums that are used to execute module forperforming various activities such as configuring mobile bugs 105,configuring mobile devices 107, exchanging data over the networks 123,125 and storing data in support of one or more agencies, monitoringdevices, and operated mobile bugs. For example, the agency service 115may include one or more modules providing ascribed functionality to anagency and monitoring devices via an application programming interface(“API”) or web interface, collectively “the monitoring interface”, asdescribed in more detail with reference to FIG. 1C. The agency service115 may also include infrastructure for providing audio and videocommunicability (e.g., internally and/or over a network) within themonitoring interface using the public switched telephone network(“PSTN”), voice over internet protocol (“VoIP”) and video conferencingservices.

The mobile bugs 105 are oftentimes mobile telephonic devices capable ofcollecting data and transmitting data (e.g., wirelessly) over thetelephony network 125A. Additionally, some mobile bugs 105 may includeconnectivity to the internet 123 to transmit collected data to theagency service 115 in real-time or when a connection to the internetbecomes available. Some examples of a mobile bug 105 include a mobilephone, tablet or notebook computer. Example embodiments of the mobilebug as a mobile phone include feature phones, smart phones or standardmobile phones. Accordingly, a given mobile phone or other deviceoperated as a mobile bug 105 may not necessarily include or support allof the functionality ascribed herein to the mobile bug or mobile bugsystem due to inherent differences in device capabilities. In someembodiments, other telephonic devices such as land-line phones are used.

In one embodiment, the mobile bug 105 executes a bug module forcollecting data, transmitting data and maintaining a persistentconnection for transmitting audio and/or other collected data. Anexample embodiment of a bug module is described in more detail withreference to FIG. 2.

In addition to the mobile bugs 105, a number of monitoring devices 107may connect to an available network 123, 125 to obtain or present datacollected from one or more of the mobile bugs. Depending on theembodiment, a monitoring device 107 is a telephonic device that can beoperated within the agency or externally in the field. As referred toherein, a monitoring device 107 is a mobile or stationary telephonicdevice capable of connectivity (e.g., wireless or wired) to a networksuch as an internal agency network, the internet 123, PSTN and/orcellular network 125. Some examples of a monitoring device 107 include amobile phone, land-line phone, tablet and notebook or desktop computer.

Example embodiments of the monitoring device 107 as a mobile phone caninclude feature phones, smart phones or standard mobile phones.Accordingly, a given mobile phone or other device operated as amonitoring device 107 does not necessarily include or support all of thefunctionality ascribed herein to the monitoring device or the mobile bugsystem due to inherent differences in device capabilities. In oneexample embodiment, the monitoring device 107 executes a monitoringmodule for interfacing with entities on a network 123, 125 to managemobile bugs 105 and view collected data.

As used herein, the term “module” refers to computer programinstructions and/or other logic used to provide the specifiedfunctionality. Thus, a module can be implemented in hardware, firmware,and/or software. In one embodiment, program modules formed of executablecomputer program instructions are stored on a non-transitory storagedevice, loaded into memory, and executed by a computer processor as oneor more processes.

FIG. 1B is a block diagram illustrating an environment 100 b forimplementing a system for a mobile phone as a one-way recordedtransmitter “mobile bug” activated through a relay according to anexample embodiment. As shown, the environment 100 b includes a telephonynetwork 125B, where virtual numbers 101 are available, that couplesrelay 113, mobile bug 105, monitoring device 107, and agency service115. The embodiment of FIG. 1B differs from that of FIG. 1A in that therelay 113 need not be implemented to support mobile bug 105 andmonitoring device 107 operation on a telephony network other thantelephony network 105B. However, similar to the embodiment of FIG. 1A,the relay 113 may be implemented to enable mobile bug 105 and monitoringdevice 105 operation via message communications through the relay 113where an agency prefers such operation. Accordingly, the relay 113 maypass messages between the devices and the agency service 115 via theinternet 123 and/or the telephony network 125B in a fashion similar tothat described with reference to FIG. 1A. Additionally, in theconfiguration of FIG. 1B, the agency service 115 may include the relay113 and/or utilize a virtual number 101 provisioned with a provider tomimic relay functionality by instructing the provider of the virtualnumber to the perform functions of the relay through the virtual number.

FIG. 1C is a block diagram illustrating an operating environment 101 ofa mobile bug 105 activated through a relay 113 according to an exampleembodiment. As shown, the operating environment 101 includes a network120 with components such as the internet 123, telephony 125 and provider127 networks. The network 120 may also include GPS satellites (notshown) that transmit position data to mobile bugs 105 and other devices.

The network 120 represents the communication pathway between relay 113,agencies 110, agency services 115, mobile bugs 105, monitoring devices107 and other entities (not shown). In one embodiment, the network 120includes standard communications technologies and/or protocols and caninclude the Internet and PSTN. Oftentimes, these communicationstechnologies and/or protocols carry both PTSN and Internet related data.Thus, the network 120 can include links using technologies such asEthernet, 802.11, worldwide interoperability for microwave access(WiMAX), 2G/3G/4G mobile communications protocols, worldwideinteroperability for PSTN communications, digital subscriber line (DSL),asynchronous transfer mode (ATM), InfiniBand, PCI Express AdvancedSwitching, etc. Similarly, the networking protocols used on the network120 can include multiprotocol label switching (MPLS), the transmissioncontrol protocol/Internet protocol (TCP/IP), the User Datagram Protocol(UDP), the hypertext transport protocol (HTTP), the simple mail transferprotocol (SMTP), the file transfer protocol (FTP), etc. The dataexchanged over the network 120 can be represented using technologiesand/or formats including analog audio (e.g., for last mile PSTNcommunications), digital audio and video (e.g., as a file or streamingwith Real Time Streaming Protocol), the hypertext markup language(HTML), the extensible markup language (XML), JavaScript, VBScript,FLASH, the portable document format (PDF), etc. In addition, all or someof the data exchanged over the network 120 can be encrypted usingconventional encryption technologies such as secure sockets layer (SSL),transport layer security (TLS), virtual private networks (VPNs),Internet Protocol security (IPsec), etc. In another embodiment, theentities on the network 120 can use custom and/or dedicated datacommunications technologies instead of, or in addition to, the onesdescribed above. For example, some government agencies and the militarymay operate networks auxiliary to the internet and PSTN.

The telephony networks 125A, 125B may include servers, switches andother hardware and software for implementing, among other protocols andtechnologies, worldwide interoperability for PSTN communicationsincluding land-lines and 2G/3G/4G wireless protocols. The telephonynetworks 125A, 125B may also provide mobile devices with the capabilityto transmit and receive data over the internet 123. A telephony network125 (e.g., 125B) may managed by one or more communication serviceproviders “CSPs” (not shown) that own telephone numbers for use on thePSTN and the CSPs own network (e.g., a wireless network thatcommunicates with the PSTN). However, as described previously, ininstances where the capabilities of telephony network 125B and telephonynetwork 125A differ, relay 113 may be implemented to facilitateconfiguration of mobile bugs 105 and monitoring devices 107A on thetelephony network 125A. Thus, the agency service 115 can manageactivation of the mobile bug 105 and monitoring of the mobile bug on onetelephony network 125A through another telephony network 125B and theprovider 127 associated with telephony network 125B.

The provider 127 may include servers, switches and other hardware andsoftware for communicating over the network 120 with CSPs and otherentities. The provider 127 buys or leases numbers for use on thetelephony network 125B from multiple CSPs. The provider 127, in turn,manages numbers provisioned for use by the agency service 115 and thetelephony traffic associated with the numbers on telephony network 125B.In one embodiment, the agency service 115 provisions one or more of thenumbers as virtual numbers with the provider 127 over the network 120.

Typically, a number used on the telephony network 125 directs to a givenmobile device, VoIP device or land-line device having an associatednumber identity characterized by automatic number identification “ANI”information, or caller identification. In the case of virtual numbersprovisioned for use on telephony network 125B, the virtual numbers,while still operable with the PSTN and CSP networks, are associated withthe provider 127 who handles telephony traffic for the number. Because avirtual number does not direct to an end user device, the provider 127may establish connections with devices dialing into the virtual number,establish connections with devices by dialing out to the devices fromthe virtual number, record call information such as call audio andcaller history (e.g., on a computer readable medium) and stream/providecall information for download (e.g., over the network 120 such as viathe internet 123).

The provider 127 may also pass/bridge audio (bidirectional orunidirectional) in real-time between two or more telephonic devices withconnections established through the virtual number (or connected withthe provider 127 via a virtual number). Additionally, as the virtualnumbers are handled by the provider 127, the agency service 115 maymodify ANI information and caller identification associated with thevirtual number.

In addition to provisioning virtual numbers for the agency service 115,the provider 127 communicates notifications and data associated with thevirtual numbers to the agency service 115 or other entity such as theagency 110. For example, the provider 127 may notify the agency service115 of an incoming call from a device to the virtual number and receiveinstructions from the agency service 115 to connect the device to thevirtual number. The provider 127 may also receive instructions from theagency service 115 to dial out to a device such as the mobile bug 105 ormonitoring device 107 from the virtual number. Additionally, theprovider 127 may receive instructions to stop/start recordings of audioassociated with the mobile bug 105 and/or monitoring the mobile bug 105on the virtual number and interface with a transcription service totranscribe call audio. In turn, the provider 127 can transmit therecordings and transcripts to the agency service 115 or other entity onthe network 120. In addition, the provider 127 may pass messagesreceived at the virtual number to the agency service 115 and receiveinstructions for transmitting messages from the virtual number from theagency service 115.

Additionally, the provider 127 may enable or disable inbound and/oroutbound audio for different parties being connected to the virtualnumber and recordings thereof responsive to instructions received (e.g.,via an API) from the agency service 115. The provider 127 can receiveinstructions for managing a virtual number as part of the provisioningprocess, prior to an incoming call or outbound call on the virtualnumber, or in real-time from the agency service 115 when connecting adevice through the virtual number. In some embodiments, the provider 127communicates directly with the agency 110 to provision virtual numbers,transmit notifications and data or receive instructions, in which casethe agency 110 may incorporate the functionality of the agency service115. Additionally, the provider 127 itself may function as a CSP andvice versa.

In an embodiment, the agency service 115 receives requests forprovisioning a virtual number and registering mobile bugs 105 and/ormonitoring device 107A with the virtual number through the relay 113.The requests may originate from a telephonic device such as the mobilebug 105 or monitoring device 107A, which the relay 113 passes to theagency service 115. The agency 110 and other monitoring device 107B,107C may also provision virtual numbers through an API with the agencyservice 115. The requests can include number information forprovisioning virtual numbers such as an area code (e.g., 555), countrycode (e.g., +44) and/or associated CSP. In some embodiments, the agencyservice 115 determines the number information for the virtual numberbased on the number information associated with the relay 113 and/orrequesting device. In turn, the agency service 115 queries the provider127 for available virtual numbers matching the number informationcorresponding to the request. The agency service 115 subsequentlyreceives available virtual numbers from the provider 127 and claims avirtual number with the desired number information from the provider127. The agency service 115 generates one or more PINs for registeringdevices with the virtual number. For example, the agency servicer 115may generate a transmitting PIN and a monitoring PIN for registering atelephonic device as either a mobile bug (transmitter) or a monitoringdevice (monitor).

The agency service 115 transmits the registration PINs to the relay 113,which in turn transmits a message including the PINs and information forthe virtual number (e.g., the number information for the virtual number)to the telephonic device (e.g., the mobile bug 105 or monitoring device107A) having requested provisioning of the virtual number. The relay 113may subsequently receive a registration request message from atelephonic device. The registration request message may include contentsuch as a PIN to register the telephonic device or other telephonicdevice with the virtual number. The message identifies the registrationrequest for the telephonic device as a request for registering either amonitoring device 107A or mobile bug 105 (e.g., by the provided PIN) andincludes identifying device information, such as number informationand/or transmitting number for the monitoring device 107A or mobile bug105. The device information for the requesting telephonic device such astransmitting number and associated number information may be included inmessage header information (e.g., “from” field) or identified in thecontents of the message. The relay 113 passes the received message(e.g., including header information and content) to the agency service115 to register a mobile bug 105 and/or monitoring device 107A with thevirtual number.

In some embodiments, a PIN is an authorization code included in thecontent of the message for authorizing registration of a device with thevirtual number. In some embodiments, a unique monitoring PIN formonitoring devices and transmitting PIN for a mobile bug are generatedsuch that a user of either device need only include the appropriate PINin a message transmitted to the relay from the corresponding device toregister with the virtual number. In other embodiments, a single PIN maybe generated and additional content (e.g., “bug” or “monitor” indicator)of the message indicates how the requesting device should be registered.In some embodiments, where the requesting device desires to registeranother device as either a mobile bug 105 or monitoring device 107,device information such as the transmitting number for the other devicemay be included as content in addition to the corresponding PIN orsingle PIN and bug/monitor indicator.

The agency service 115 may optionally allow an entity on the network 120to specify ANI and/or caller identification associated with the virtualnumber to spoof the number's identity on the network 120. The agencyservice 115, in turn, transmits instructions to the provider 127 formodifying the number identity. The agency service 115 may optionallyverify the spoofed number identity. When a virtual number is no longerneeded by the agency 110, the agency service 115 obtains any audiorecordings or call logs associated with the virtual number and releasesthe number back to the provider 127.

In one embodiment, the agency service 115 stores mapping information forvirtual numbers in a mapping table. The mapping information for avirtual number may include number information for the virtual number,one or more generated PINs, and device information for mobile bugs andmonitoring devices registered with the virtual number. For example, themapping information may include a virtual number, one or moreauthorization PINs for registering a device with the virtual number, thetransmitting number of a registered mobile bug 105 and/or and monitoringdevice 107, and a device identifier indicating whether the device isregistered mobile bug or monitoring device (which in some embodiments,may be implied by a PIN prefix and/or suffix). Thus, for example, theagency service 115 stores mapping information for provisioned virtualnumber in response to received requests for virtual numbers and inresponse to registration requests associated with the virtual number. Inturn, the agency service 115 may determine, from the mapping table, thevirtual number and/or devices to which connections should be establishedto/from during an operation. One example mapping may specify a claimedvirtual number for use as a virtual number (receiving number) for amobile bug 105 to be connected with in order to transmit collected data(e.g., audio) over a telephony network (e.g., 125A). Additionally, themapping for the receiving number may specify one or more monitoringdevices 107 permitted to monitor the mobile bug 105, and to whichconnections may be established with through the virtual number when themobile bug begins transmitting collected data. As multiple monitoringdevices 107A, 107B, 107C may monitor a mobile bug 105 registered with areceiving number, the agency service 115 may register multiplemonitoring devices with the receiving number and by storing multipletransmitting numbers of monitoring devices in association with thereceiving number in the mapping table.

In practice, agency service 115 consults the mapping table toautomatically identify a receiving number associated with a registeredmobile bug 105 requesting to activate a session where data is collectedfrom the mobile bug 105. The agency service 115 may receive the requestto activate the session in the form of a message originating from themobile bug 105 and passed (e.g., with message header information andmessage content) to the agency service by the relay 113. For example, inresponse to receiving a request to activate a mobile bug 105, the agencyservice 115 identifies the corresponding receiving number and transmitsinstructions to a provider 127 causing the mobile bug 105 to receive aconnection request from the identified receiving number. The agencyservice 115 may additionally instruct the provider 127 to configure theconnection such that outbound audio to the mobile bug 105 is disabled.Accepting the connection request at the mobile bug 105 activates thesession. Additionally, the agency service 115 may consult the mappingtable to automatically identify one or more monitoring devices 107registered with the receiving number, and thus permitted to monitor thesession in real-time and/or receive the collected data from the session.In turn, in response to receiving the request to activate the mobile bug105, the agency service 115 may transmit instructions to the provider127 causing the one or more registered monitoring devices 107 toautomatically receive a connection request from the identified receivingnumber. In turn, a monitoring device 107 may accept the connectionrequest to monitor the active session.

Personnel with a registered monitoring device 107 that desire to monitorthe mobile bug 105 with a mobile or land-line phone in the field mayalso transmit a request to monitor a session (which may be ongoing) tothe relay 113, in which case the agency service 115 identifies thereceiving number associated with the registered monitoring device 107and transmit instructions to the provider 127 causing the registeredmonitoring devices 107 to receive a connection request from theidentified receiving number to monitor the active session. In manycases, a monitoring device 107 may be utilized to monitor multiplemobile bugs 105. Accordingly, the request to monitor a session mayinclude a monitoring PIN associated with the receiving number and/or thereceiving number the monitoring device 107 desires to monitor such thatthe agency service 115 may identify a specific receiving number frommultiple ones the monitoring device 107 is registered with in themapping table.

The agency service 115 may also otherwise notify (e.g., a text messageor email) monitoring devices when the mobile bug 105 request to activatea session. The agency service 115 may also notify monitoring devices 107through the monitoring interface 145 or via text massage or email.

In some embodiments, the agency service 115 includes a bug module 135which may be provided to the mobile bug 105. The bug module 135interfaces with the native dialer of the mobile bug 105 to manageconnections with a selected virtual number such as the receiving numberand/or interfaces with a messaging application of the mobile bug 105 tomanage messages with a selected relay 113. Additionally, the bug module135 may interface with mobile bug 105 software and/or hardware toutilize features such as an image capture device and GPS to collectreal-time image or video and position data. The bug module 135 transmitsthe collected data over the network 120 back to the agency service 115either continually or periodically (e.g., via the internet 123) or otherentity. The agency service 115, in turn, may store the collected datafor transmission to one or more monitoring devices 107 and the agency110. Furthermore, the bug module 135 may be configured with a passwordor otherwise disguised when executed to prevent users other than theoperator from accessing the module altogether and/or particular featuresthat would give away its true nature. The bug module 135 is described inmore detail with reference to FIG. 2. In instances where the mobile bug105 is coupled to telephony network 125A, the bug module 135 maytransmit and receive information to/from the agency service 115 inmessage format via the relay 113.

In some embodiments, the agency service 115 includes a monitoringinterface 145 for providing data received from mobile bugs 105 tovarious monitoring devices 107 and/or appliances 150 over the network120. For example, the monitoring interface 145 may provide monitoringdevices 107 with data or notifications corresponding to the status(e.g., transmitting or disconnected) of one or more mobile bugs 105. Insome embodiments, for monitoring devices 107A on telephony network 125A,the monitoring interface 145 may provide the data and notifications tothe relay 113 and identify the monitoring device 107A to which the relay113 should transmit the information. For example, the monitoringinterface 145 may format notifications and received data into a messagefor transmission to the monitoring device 107A (e.g., over telephonynetwork 125A) and provide the message for transmission to the relay 113(e.g., over internet 123). If the mobile bug 105 is transmittingreal-time data, the monitoring interface 145 can stream data such asaudio from the active transmission, GPS coordinates with heading, speedand coordinates of last-reported locations for placement on a map,collected image or video data, and the internet protocol address and/ortelephone numbers of other personnel monitoring or having access to themobile bug. In some embodiments, the monitoring interface 145 syncscollected data prior to transmission or includes tags in the transmitteddata for synchronization of playback at a monitoring device 107. Themonitoring interface 145 can also stream, or provide for download,previously recorded sessions.

In some embodiments, the agency service 115 provides a monitoring module140 to monitoring devices 107 for accessing the monitoring interface145. The monitoring module 140 transmits requests associated withprovisioning a virtual number and/or registering devices with a virtualnumber, and receiving real-time data collected by monitored bugs via therelay 113 and/or internet 123. For example, the monitoring module 140may provide a user interface or status dashboard with options forrequesting provisioning virtual numbers, registering a transmittingnumber of a mobile bug 105 or monitoring device 107 to a given virtualnumber and PIN information for virtual number. In one embodiment, thedashboard provides an option to toggle a recording session on or offwith the agency service 115. When the recording session is disabled, themonitoring device 105 still receives real-time data, but the agencyservice 115, appliance 150 and provider 127 do not store copies of thecollected data.

The monitoring module 140 may also display real-time status informationfor the mobile bug 105 including current GPS location, tracked GPSlocation, live audio and image data, mapping table information and otherinformation collected from the mobile bug and streamed by the monitoringinterface 145. Similarly, the monitoring module 140 may be used toaccess and playback historic activity associated with a given virtualnumber or mobile bug 105. For example, the monitoring module 140 maydownload files for playback or steam them. In addition to interfacingwith the agency service 115, the monitoring module 140 may interfacewith an appliance 150 that stores (or backs up) collected data withinthe agency 110. Additionally, the monitoring module 140 may includefunctionality of the bug module 135 and vice versa.

In instances where the monitoring device 107A is coupled to telephonynetwork 125A, the monitoring module 140 may transmit and receiveinformation to/from the agency service 115 in message format via therelay 113.

Agency 110 represents a collection of servers, desktop, notebook ortablet computers, mobile telephones and related storage mediums used byrespective agency personnel for executing applications or modules tocommunicate with and receive data from the agency service 115 (e.g., viathe monitoring interface) and other entities on the network 120. Forexample, agency 110 devices may execute a web browser to access a webinterface or execute a mobile or desktop application for communicatingwith an API provided by the agency service 115. An agency 110 may alsoinclude telephonic and video infrastructure enabling audio and videocommunicability (e.g., internally and/or over the network 120) using thepublic switched telephone network (“PTSN”), voice over internet protocol(“VoIP”) and video conferencing services for monitoring or specifyingconfigurations for mobile bugs 105.

In one embodiment, the agency 110 includes an appliance 150 for storingdata collected by mobile bugs 105. The appliance 150 may utilize themonitoring interface 145 provided by the agency service 115 for updatingstored data or receive data directly from mobile bugs 105. Additionally,the appliance 150 may receive audio recorded on a virtual number andassociated transcripts from the provider 127 or agency service 115. Oneexample embodiment of the appliance 150 also includes its own monitoringinterface (not shown) that enables monitoring devices 107 to accessreal-time and historic data stored on the appliance for the mobile bug105. Monitoring interfaces provided by the agency service 115 orappliance 150 may also be accessible via a web browser for streaming ordownloading data and include the same or similar options.

Additionally, the appliance 150 and agency service 115 may communicateto intermittently update collected data and records at defined intervalsor in response to notifications to download data. During the intervalsor notification periods, the agency service 115 may process the data andperform any necessary actions as desired in support of mobile bugs 105or monitoring device 107 until the data is transferred to the appliance150. In some embodiments, the agency service 115 maintains a persistentconnection with the appliance 150 to facilitate transfer of real-timedata collected by mobile bugs 105 operated in the field.

In one embodiment, the agency service 115 ensures that it, and theprovider 127, do not possess data collected by mobile bugs 105 beyondthe time needed to facilitate transfer. However, in mission criticalsituations, operators and other agency 110 personnel cannot rely only onthe availability of the appliance 150 for storing and maintainingcollected data. Consequently, if the appliance 150 is unable to takepossession of the collected data or go offline during transfer, theagency service 115 and/or the provider 127 may maintain possession ofthe collected data until the appliance 150 is functioning. Furthermore,the agency service 115 and/or provider 127 may determine whetherchecksums, hashes or sizes of transferred data match the appliance's 150version prior to deleting stored data.

In some embodiments, the agency service 115 maintains an applianceinstead of, or in addition to, the agency 110. In such cases, theappliance may exist as a dedicated piece of hardware or remote storage.Alternatively, embodiments of the appliance 150 may be implemented in acloud computing and storage stack available on the network 120.

Mobile Bug Functionality

FIG. 2 is a block diagram illustrating a bug module 135 according to oneexample embodiment. As mentioned above, the bug module 135 may bedownloaded from the agency service 115 to the mobile bug 105 andexecuted to collect and transmit data to entities on the network 120. Asshown in FIG. 2, the bug module 135 itself includes multiple modules. Inthe embodiment shown in FIG. 2, the bug module 135 includes a messagemodule 203, connection module 205, GPS module 210, imaging module 215,and protection module 220. In some embodiments, the functions aredistributed among the modules in a different manner than describedherein. Other embodiments have additional and/or other modules.

The message module 203 manages communications between the mobile bug 105and a specified relay 113. For example, the transmitting number of arelay 113 may be stored at the messaging module 203. In turn, themessaging module 203 may include an interface for viewing messagesreceived from the relay and transmitted to the relay. The messagingmodule 203 and/or protection module 220 may monitor inbound and outboundmessages of the mobile bug 105 and intercept messages to/from the relaysuch that the messages do not appear in the native messaging applicationor in visual and/or audible notifications of the mobile bug 105.Additionally, messaging module 203 interface may include a command setto aid users in composing messages to the relay 113. For example, thecommand set (e.g., “new,” “register device,” “activate,” “stop” orsimilar) may generate a formatted message including any additional inputoptions for transmission to the relay 113 and configured to,respectively, request a new virtual number, register a device with avirtual number, activate a session, and stop a session when once passedvia the relay 113 to the agency service 115. The options to request avirtual number may include an authorization code permitting use of thesystem and/or desired number information for spoofing the caller ID ofthe virtual number. The options for registering with the virtual numbermay include a specified PIN, transmitting number, device identifier,and/or other information describing the device to register.

The connection module 205 manages connections between the mobile bug 105and a virtual number such as the receiving number mapped to thetransmitting number of the mobile bug 105. For example, the operator maymove into an area without network service and unknowingly disconnect themobile bug 105 from the receiving number or otherwise prevent successfultransfer of data to an entity on the network. The connection module 205receives input from the operator including the receiving numberassociated with the mobile bug 105. If number information for thereceiving number has been spoofed, the connection module 205 may receiveinput for the spoofed number information. In turn, the connection module205 may automatically identify connection requests from the receivingnumber (with or without spoofed number information) for activating themobile bug and automatically accept the connection request to establishor reestablish a connection with the receiving number. For example, theconnection module 205 may automatically accept connection requests fromthe receiving number after a request to activate a session istransmitted to the relay and until a request to stop the session istransmitted to the relay. In one embodiment, once a connection isestablished through the receiving number after a request to active asession is transmitted, the connection module 205 may detect networkdisruptions such as dropped calls and automatically instruct the messagemodule 203 to re-request activation of the session without input fromthe operator of the mobile bug 105. The connection module 205 mayfurther modify a call log associated with the native dialer such thatconnection requests from the receiving number do not appear in thenative dialing application and/or call log.

Depending on the mobile bug's 105 capabilities, the communication module205 may enable placement/receipt of outgoing and incoming calls (e.g.,other than those established by module to the receiving number) duringmonitoring (e.g., via call waiting features) within the native dialerapplication or similar. Embodiments of the communication module 205and/or protection module 220 may suppress visual notifications or queuesthat the communication module 205 is maintaining a connection throughthe receiving number. In some instances, the communication module 205can pass audio from the inbound or outbound call to the call-waitingconnection with the receiving number to prevent gaps in audiomonitoring.

The GPS module 210 communicates with a native GPS receiver on the mobilebug 105 to receive GPS location data. The GPS module 210 may alsocommunicate with other radio receivers and directional mechanisms (e.g.,compass or accelerometers) on the mobile bug 105 to receive additionallocation data. The GPS module 210 processes the GPS and radio locationdata to determine and refine an estimated location measurement for themobile bug 105. The location measurement may include, but is not limitedto, latitude, longitude, altitude, heading, speed, associated accuracymeasurement and the time and date of recording. The GPS module 210 maytransmit the determined location measurement to the agency service 115via the relay 113 (e.g., in a message transmitted by the message module203) or via the internet 123. In one embodiment, the GPS module 210streams the location measurement in real-time via the internet 123 or acollection of locations measurements in intervals (e.g., every 5minutes) via the relay 113.

The imaging module 215 communicates with a native image sensor on themobile bug 105 for capturing still images or videos. The imaging module215 may downsample (e.g., compress) collected image data fortransmission based on available bandwidth and/or communication type(e.g., via a message such as an MMS to the relay). High-resolution imagedata may be stored directly on the device for subsequent transmission asa high-bandwidth connection (e.g., WiFi) becomes available.

In some embodiments, a protection module 220 interfaces with theoperating system of the mobile bug 105 to provide options orfunctionality for concealing operations of the bug module 135 on themobile bug 105. For example, the protection module 220 providesoperators with option to run the bug module 135 in the background andonly reveal or access the bug module in response to a specified key-in(e.g., button-press combination, password or other personalidentification). In another example, the protection module 220 mimicsthe look and feel of the native operating system, calling and/ormessaging application on the mobile device to conceal use of bug module135 functionality. However, unlike the native operating system orapplications, the protection module 220 provides password protection,locking (e.g., with a key-in) or otherwise visually concealed orprotected configuration options and viewing of current call activity forconnections established by the communications module 205 and messages inthe message module 203 to/from the relay 113.

In some embodiments, the bug module 135 and the modules thereininterface and communicate with non-native devices attached to the mobilebug 105. For example, audio, images and locations data can be determinedfrom accessories coupled (e.g., wired microphone or imaging device) orwirelessly connected (e.g., Bluetooth headset) to the mobile bug 105.

Virtual Number Provisioning and Device Registration

FIG. 3A is an interaction diagram illustrating a method for requesting avirtual number and registering a mobile bug and/or monitoring devicewith the virtual number through a relay 113, according to exampleembodiments. The relay 113 receives 310 a message requesting a virtualnumber for operating a mobile bug 105 (e.g., a message with messagecontent “new”). The message may originate from a telephonic device suchas the mobile bug 105 or monitoring device 107. The relay 113 forwards320 the message requesting the virtual number to the agency service 115.The forwarded message may include the original message such that theagency service 115 may inspect original header information in additionto message content. In some embodiments, the message content includes anauthorization code that when authenticated by the agency service 115permits the requesting device to obtain a virtual number for utilizingthe system.

In some embodiments, because the relay 113 may receive messages from anydevice capable of messaging the relay, the authorization code ensuresthat only requests for a new virtual number for operating a mobile bug105 that include an approved authorization code are processed by theagency service 115. An example request including an authorization codemay include a message with message content “new [authorization code]”.The request may further include spoofed number information for thevirtual number, such that the caller ID of the virtual number whendialing out to telephonic devices differs from the virtual numberitself.

Additionally, unique authorization codes may be assigned to differentagencies and/or system accounts to track billing/reporting, or in theevent that multiple agencies share the same relay 113, indicate to whichagency a virtual number for operating a mobile bug belong. For example,Agency A may utilize the same relay 113 as Agency B over telephonynetwork 125A in Colombia, but Agency A may request a virtual number foroperating a mobile bug with “new 1111” and Agency B with “new 2222”.

The agency service 115 provisions 340 a virtual number and maps thevirtual number to one or more PINs. For example, a transmitting PIN fora mobile bug and monitoring PIN for a monitoring device may be mapped tothe virtual number. Alternatively, a generic PIN may be generated, whichmay simply be the virtual number. The agency service 115 generates 353 aconfirmation message including the one or more PINs and the virtualnumber (or spoofed number information specified for the virtual number),which is passed to the relay 113 with instructions for transmitting theconfirmation message to the device having originated the request. Theagency service 115 and/or relay 113 may identify the originating devicefrom the original header information of the message requesting thevirtual number. In turn, the relay 113 transmits 353 the confirmationmessage to the device having originated the request. The user of thedevice having originated the request may pass PIN(s), and/or relayinformation to other users for registration of devices with the virtualnumber. Additionally, the user of the device having originated therequest may provide other users with the virtual number (or spoofednumber information for the virtual number) such that mobile bug and/ormonitoring device users may store the virtual number or the spoofednumber information on their devices or visually identify connectionrequests associated with operating a mobile bug or monitoring device. Inthe case of a mobile bug, the virtual number or spoofed numberinformation for the virtual number may be stored in a bug module toautomate acceptance of connection requests for activating the mobilebug.

With a virtual number provisioned and mapped 340 by the agency service115, a device may request to register with the virtual number throughthe relay 113. The relay 113 receives 360 a message requesting toregister with a virtual number for operating a mobile bug 105 ormonitoring device 107. The message may originate from a telephonicdevice such as the mobile bug 105 or monitoring device 107. The relay113 forwards 363 the message requesting to register the device with thevirtual number to the agency service 115. The forwarded message mayinclude the original message such that the agency service 115 mayinspect original header information in addition to message content. Themessage content may include a mobile bug or monitoring device specificPIN or a generic PIN with device identifier (e.g., mobile bug ormonitor) identifying the requesting device as either a monitoring deviceor the mobile bug for registration. In some embodiments, the generic PINis the virtual number. The header information includes deviceinformation such as the transmitting number of the device originatingthe request. In some embodiments, the message content may include atransmitting number of a device to register such that a given device mayregister another device with the virtual number. The agency service 115identifies the virtual number mapped to the PIN included in the messagecontent from the mapping table. The agency service 115 identifieswhether the device for registration is a monitoring device or mobile bugbased on the PIN and/or device identifier in the message content. Theagency service 115 identifies device information for the device toregister from the original header information or the message content.

The agency service 115 maps 365 the identified device information to theidentified virtual number to register a mobile bug or monitoring devicewith the virtual number. The mapping 365 may include the deviceidentifier (e.g., in instances where a generic PIN is utilized). Ininstances where unique PINs are ascribed to the mobile bug andmonitoring devices, the PIN may serve as a device identifier.

The agency service 115 generates 367 a confirmation message indicatingsuccessful registration of the identified device to the identifiedvirtual number as either the mobile bug or a monitoring device, which ispassed to the relay 113 with instructions for transmission to the devicehaving originated the request. In turn, the relay 113 transmits 369 theconfirmation message to the device having originated the request. Inconfigurations where the device originating the request differs from thedevice indicated for registration (e.g., by device information inmessage content), an additional confirmation message may be generatedand transmitted to the device that was registered.

FIG. 3B is an interaction diagram illustrating a method for provisioning340 and mapping virtual numbers for operating and monitoring a mobilebug according to one example embodiment. Initially, the agency service115 receives 341 a request for provisioning a virtual number from amonitoring device 107, mobile bug 105, or other entity. The request forprovisioning 341 the virtual number may be received from a relay 113 andoriginate from, for example, a monitoring device 107 or mobile bug 105.The agency service 115 may determine number information such as an areacode and/or country code for provisioning the virtual number based onnumber information in the request such as the number informationassociated with the device that originated the request, numberinformation specified in the request, or number information associatedwith the relay.

The agency service 115 queries 343 the provider for virtual numbersmatching the determined number information for provisioning the virtualnumber. The provider 127 returns 345 a list of available virtual numbersto the agency service 115 matching the specified number information tothe agency service 115. If no matching virtual numbers are available,such as in instances where a relay 113 supports communications with atelephony network other than those associated with the provider, theagency service 115 may request available virtual numbers from theprovider that need not match the specific number information. The agencyservice 115 claims 347 a virtual number from the provider 127. Theagency service 115 may optionally modify corresponding ANI and calleridentification information for the virtual number based on instructionsfrom the requesting device or via the interface. The agency service 115subsequently stores the modified virtual number information andinstructs the provider 127 to update the associated virtual numberinformation.

With a virtual number claimed, the agency service 115 generates 349 oneor more PINs and maps 350 the PINs to the virtual number. For example,the agency service 115 may generate and map a transmitting PIN forregistering a mobile bug 105 with the virtual number to operate thevirtual number as a receiving number for the mobile bug. Additionally,the agency service 115 may generate and map a monitoring PIN forregistering monitoring devices 107 with the virtual number to permitmonitoring of the mobile bug.

In some embodiments, the agency service 115 may prompt the requestingdevice to provide the PIN or modify an automatically generated PIN. Forexample, the agency service 115 may generate a message for transmissionto the requesting device by the relay 113 with “reply to specify atransmitting PIN and/or monitoring PIN e.g., [transmitting PIN][monitoring PIN]” or similar. In turn, the relay 113 passes a replyreceived to the message to the agency service 115 which maps the PIN(s).The agency service 115 may identify the reply as associated with therequest by the matching header information of the requesting devicetransmitting messages to the relay. The agency service 115 may confirmsuccess of PIN mapping in a confirmation message passed to therequesting device via the relay.

Alternatively, the agency service 115 may map the generated PINs andinclude in a confirmation message passed by the relay to the requestingdevice “Transmit PIN: [T1111] monitor PIN: [M2222] reply to specify acustom transmitting PIN and/or monitoring PIN e.g., [transmitting PIN][monitoring PIN]” or similar. Accordingly, the user of requesting devicemay reply to alter a automatically generated PIN and subsequentlyreceive a confirmation from the agency service 115 via the relay.

FIGS. 3C and 3D are tables illustrating example embodiments of virtualnumber mapping 350 to PINs for operating and monitoring a mobile bug. Asshown in FIG. 3C, mapping table 370A includes a mapping 340 ofprovisioned virtual numbers as receiving numbers for operating andmonitoring a mobile bug. Each receiving number 373 is mapped to agenerated PIN. The agency service 115 may store a virtual number as areceiving number 373 in the mapping table 370A once the virtual numberhas been provisioned with a provider 127. In turn, according to anexample embodiment, the agency service 115 generates a uniquetransmitting PIN 371 and monitoring PIN 375 that are mapped to thereceiving number 373. Thus, a registration request including atransmitting PIN 371 (e.g., T12345) identifies a device for registrationas the mobile bug with the corresponding receiving number 373 (e.g., +44555-111-2222) in the mapping table 370A. For example, the agency service115 may receive a registration request originating from a telephonicdevice with a transmitting number of “555-555-5555” including the PIN“T12345” to register the telephonic device as the mobile bug withreceiving number “+44 555-111-2222.” Similarly, a registration requestincluding a monitoring PIN 375 (e.g., M12345) identifies a device forregistration as a monitoring device of the corresponding receivingnumber 373 (e.g., +44 555-111-2222) in the mapping table 370A. Forexample, the agency service 115 may receive a registration requestoriginating from a telephonic device with a transmitting number of“555-666-6666” including the PIN “M12345” to register the telephonicdevice as a monitoring device with receiving number “+44 555-111-2222.”

FIG. 3D is a table illustrating an example embodiment of virtual numbermapping 365 to devices for operating and monitoring a mobile bug 105.Mapping table 370B includes a receiving number 373 mapped to a mobilebug and a monitoring device in response to the above exampleregistration requests. In some embodiments, the information of mappingtables 370A, 370B may be maintained in a single mapping table, althoughthey are illustrated separately for ease of explanation.

As shown in mapping table 370B, receiving number 373 “+44 555-111-2222”is mapped to the device information 378, i.e., transmitting number“555-555-5555” of the mobile bug that originated the registrationrequest including transmitting PIN 371 “T12345.” The mapping table 370Bmay include the PIN 377 (e.g., “T12345”) a device was registered with toidentify whether the device is a mobile bug or monitor device.Alternatively, the mapping table 370B may include an explicit device ID379 mapping, e.g., “bug” to identify the stored device information 378(e.g., transmitting number “555-555-555”) as that of the mobile bug. TheDevice ID 379 may be included in instances where a mobile bug andmonitoring devices register with a generic PIN and identify their deviceID in the registration request.

A monitoring device may register in a similar fashion as the mobile bug,and a mapping thereof in accordance with the above example registrationrequest is illustrated in mapping table 370B for a monitoring devicewith device information 378 including the transmitting number“555-666-6666.” Thus, the receiving number 373 “+44 555-111-2222” ismapped to the device information 378 “555-666-6666” of the monitoringdevice, and the monitoring device may be identified based on the PIN 377“M12345” or explicit device ID 379 “Monitor”.

Requesting to Activate a Session

FIG. 4A is an interaction diagram illustrating a method for activating400A a mobile bug through a relay according to one example embodiment.Once a virtual number is provisioned as a receiving number, and themobile bug 105 registered with the receiving number, the mobile bug 105may transmit 403 a message requesting to activate a session 403 whereactivities of the mobile bug 105 are monitored. In an embodiment, themessage is a message on a SMS. The mobile bug 105 may transmit 403 therequest to activate the session to a relay 113. In turn, the relay 113forwards 405 the message requesting to activate the session to theagency service 115.

The agency service 115 identifies device information such as atransmitting number for the mobile bug 105 from the forwarded request.For example, the agency service 115 may identify the transmitting numberin header information of the original message. In turn, the agencyservice 115 identifies a receiving number 407 associated with the deviceinformation in a mapping table. Additionally, the agency service 115identifies the device as the mobile bug 409 based on a PIN (e.g.,transmitting PIN) and/or device ID (e.g., bug) stored in associationwith the identified device information and/or the identified receivingnumber in the mapping table.

The agency service 115 instructs 413 the provider to establish a sessionwith the mobile bug through the receiving number. For example, theagency service 115 instructs the provider 127 to dial out 415 to thetransmitting number of the mobile bug 105 from the identified receivingnumber. Additionally, the agency service 115 instructs the provider 127to disable outbound audio to the mobile bug 105.

In turn, the mobile bug 105 receives a connection request from thereceiving number (which may be configured with spoofed numberinformation) and may accept 417 the connection request to activate thesession. Once the session is active, the mobile bug 105 transmitscollected audio data to the receiving number which may be monitored byone or more monitoring devices. Additionally, the mobile bug 105 maytransmit real-time data such as GPS and image data either via aninternet connection or via messages through the relay 113 to the agencyservice 115.

Requesting to Monitor a Session

FIG. 4B is an interaction diagram illustrating a method for monitoring amobile bug with a monitoring device according to one example embodiment.Once a virtual number is provisioned as a receiving number and themonitoring device 107 registered with the receiving number, themonitoring device 107 may transmit 433 a message requesting to monitor asession 433 corresponding to a period of monitored activities of themobile bug 105. In an embodiment, the message is a message on a SMS. Themonitoring device 1075 may transmit 403 the request to monitor thesession to a relay 113. In turn, the relay 113 forwards 405 the messagerequesting to monitor the session to the agency service 115.

The agency service 115 identifies device information such as atransmitting number for the monitoring device 107 from the forwardedrequest. For example, the agency service 115 may identify thetransmitting number in header information of the original message. Inturn, the agency service 115 identifies a receiving number 437associated with the device information in a mapping table. Additionally,the agency service 115 and identifies the device as the monitoringdevice 439 based on a PIN (e.g., monitoring PIN) and/or device ID (e.g.,monitor) stored in association with the identified device informationand/or the identified receiving number in the mapping table.

The agency service 115 identifies 441 whether a mobile bug 105 hasestablished an active session on the receiving number. If no session isactive, the agency service 115 may delay proceeding to step 443 until asession in active. Alternatively, the agency service 115 may proceed tostep 443 regardless of whether a session with a mobile bug is active.

In some embodiments, a monitoring device 107 registered with thereceiving number need not request 433 to monitor a session.Specifically, the agency service 115 may identify 441 when a session isactive on a receive number and, in turn, identify the device informationfor monitoring devices such as the transmitting numbers of registeredmonitoring devices associated with the receiving number in the mappingtable, and proceed to step 443.

At step 443, the agency service 115 instructs 443 the provider 127 toconnect a monitoring device 107 to a session. For example, the agencyservice 115 may instruct 443 the provider to dial out 445 to thetransmitting number of the monitoring device 107 from the receivingnumber.

In turn, the monitoring device 107 receives a connection request fromthe receiving number (which may be configured with spoofed numberinformation) and may accept 447 the connection request to monitor thesession. Once the session is active, the monitoring device 107 receivesthe collected audio data transmitted to the receiving number by theactive mobile bug. Additionally, the monitoring device 107 may receivereal-time data such as GPS and image data either via an internetconnection or via messages from the agency service 115 received throughthe relay 113.

Operating an Activated Mobile Bug

FIG. 5 is an interaction diagram illustrating a method for operating 500a mobile bug according to one example embodiment. Once the connection400A between the mobile bug 105 and the receiving number is established,the provider 127 records audio on the line from the mobile bug. One ormore of the illustrated steps may be performed automatically by a bugmodule executed on the mobile bug and/or performed manually by anoperator of the mobile bug.

The mobile bug 105 collects 510 audio data using a microphone coupled tothe mobile bug. The mobile bug 105, in turn, transmits 520 the collectedaudio data to the provider 127 by way of the connection establishedthrough the receiving number. The provider 127, in addition to enablingmonitoring devices 107 to monitor the mobile bug through the receivingnumber, transmits the audio data received from the mobile bug 105 to theagency service 115 or appliance 150 over the network 120.

The mobile bug 105 may also collect 510 image data using an image sensorcoupled to the mobile bug. The mobile bug 105, in turn, transmits 520the collected image data to the agency service 115. In some embodiments,the mobile bug 105 may transmit 520 the collected image data in amessage to the relay (not shown), which forwards the message with thecollected image data to the agency service 115 for processing. In someembodiments, the mobile bug 105 downsamples collected image data suchthat mobile bug 105 can stream image or video in real-time.

Furthermore, the mobile bug 105 may also collect 510 location data fromGPS receivers and other direction mechanism coupled to the mobile bug.The mobile bug 105 determines a location measurement including theposition of the mobile bug, direction and speed of the mobile bug andassociated accuracy of the measurement. The mobile bug 105 transmits 520the location measurement to the agency service 115. In some embodiments,the mobile bug 105 determines and transmits 520 the locationmeasurements in real-time to the agency service 115. In someembodiments, the mobile bug 105 may transmit 520 one or more locationmeasurements at defined intervals (e.g., every 5 minutes) in a messageto the relay (not shown), which forwards the message with the locationmeasurements to the agency service 115 for processing.

In some instances, the connection 400A between the mobile bug 105 andthe receiving number (e.g., via the provider 127) or the agency service115 may be terminated or timeout. In the case of a disconnection fromthe receiving number, in one embodiment the mobile bug 105 attempts toreestablish 540 the terminated connection automatically in thebackground by transmitting a request to activate a session as describedwith reference to FIG. 4A. In some embodiments, the mobile bug 105 mayautomatically receive a request to reestablish a connection and/orrequest a connection until requesting to stop the session. In eitherinstance, the mobile bug 105 may automatically accept a connectionrequest from the receiving number to maintain a persistent connectionduring an active session.

In one embodiment, the mobile bug transmits 520 data collected duringdisconnect periods in the background. For example, while the provider127 typically handles audio data via the receiving number, the agencyservice 115 may receive any audio data collected during disconnectperiods when an internet connection is and/or becomes available.Accordingly, the agency service 115 may update 530 the appliance 150with the received audio data. The agency service 115 or provider 127 canalso update 530 the appliance with any other data received from theprovider 127 and/or mobile bug 105 via the relay or internet.

Monitoring an Activated Mobile Bug

FIG. 6 is an interaction diagram illustrating a method for monitoring600 a mobile bug according to one example embodiment. As describedabove, the agency service 115 receives 610B collected data from themobile bug (e.g., via the internet and/or relay) and/or the provider127. Additionally, the provider 127 may receive data 610A from themobile bug 105. In turn, the agency service 115 and/or provider 127 mayupdate 530 the appliance at the agency 110. A monitoring device 107 maysubsequently monitor 600A, 600B the mobile bug 105 using one or both ofthe processes outlined below.

In one embodiment, the monitoring device 107 connects 400B to areceiving number for monitoring 600A the mobile bug 105. The monitoringdevice 107 may be connected 400B by answering an incoming call from thereceiving number initiated by the provider 127 once registered with thereceive number.

Once the connection between the monitoring device 107 and the receivingnumber is established, the monitoring device 640 receives the live audiotransmitted by the mobile bug through the receiving number. To continuemonitoring 600A the mobile bug 107, the monitoring device 107 simplymaintains the connection 400B with the receiving number. Additionally,the monitoring device 107 may receive messages from the agency service115 via the relay including the received data 610B from the mobile bugand/or provider, which may include some or all of the informationdescribed below with reference to monitoring process 600B.

In another embodiment, the monitoring device 107 connects 650 to theagency service 115 and/or appliance 150 for monitoring 600B the mobilebug 105. The monitoring device 107 may establish the connection 650using a web browser or monitoring module 140 that retrieves or streamscollected data via a monitoring interface on the appliance 150 or agencyservice 115 (e.g., monitoring interface 145).

In one example embodiment, the monitoring device 107 streams 660 image,audio and/or location measurements in real-time from the agency service115. In addition, the monitoring device 107 can retrieve 670 historicaldata stored on the appliance 150 to view previous mobile bug 105operating sessions 500. In some embodiments, the appliance 150 alsosupports real-time monitoring.

In some instances, the monitoring device 107 receives notifications fromthe monitoring interface 145 for display in the web browser or with themonitoring module 140. Example notifications include audio or visualalerts for notifying personnel if the mobile bug 105 stops transmittingreal-time data to the receiving number, appliance 150 or agency service115. If the mobile bug 105 reestablishes a connection, the monitoringdevice 107 may also receive notifications when real-time data streaminghas resumed or when data collected by the mobile bug 105 during thedisconnected period becomes available. As described above, some or allof the data 660, 670 and notifications may be received from the agencyservice 115 via the relay.

SUMMARY

The foregoing description of the embodiments has been presented for thepurpose of illustration; it is not intended to be exhaustive or to limitthe disclosure to the precise forms disclosed. Persons skilled in therelevant art can appreciate that many modifications and variations arepossible in light of the above disclosure.

Some portions of this description describe the embodiments in terms ofalgorithms and symbolic representations of operations on information.These algorithmic descriptions and representations are commonly used bythose skilled in the data processing arts to convey the substance oftheir work effectively to others skilled in the art. These operations,while described functionally, computationally, or logically, areunderstood to be implemented by computer programs or equivalentelectrical circuits, microcode, or the like. Furthermore, it has alsoproven convenient at times, to refer to these arrangements of operationsas modules, without loss of generality. The described operations andtheir associated modules may be embodied in software, firmware,hardware, or any combinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices.

Embodiments may also relate to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, and/or it may comprise a general-purpose computingdevice selectively activated or reconfigured by a computer programstored in the computer. Such a computer program may be stored in anon-transitory, tangible computer readable storage medium, or any typeof media suitable for storing electronic instructions, which may becoupled to a computer system bus. Furthermore, any computing systemsreferred to in the specification may include a single processor or maybe architectures employing multiple processor designs for increasedcomputing capability.

Embodiments may also relate to a product that is produced by a computingprocess described herein. Such a product may comprise informationresulting from a computing process, where the information is stored on anon-transitory, tangible computer readable storage medium and mayinclude any embodiment of a computer program product or other datacombination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the disclosure be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsis intended to be illustrative, but not limiting, of the scope of thedisclosure, which is set forth in the following claims.

What is claimed is:
 1. A computer based method for configuring abi-directional communications device as a one-way transmitter (mobilebug), the method comprising: provisioning, by a server, a virtualaddress as a receiving address; generating, by the server, without userinput as to a unique personal identification number (PIN), the PIN forregistering a bi-directional communications device as a mobile bug, thegenerated PIN stored in association with the receiving address in amapping table; receiving, by the server, a registration requestcomprising the PIN and a transmitting address of the bi-directionalcommunications device to register the bi-directional communicationsdevice as the mobile bug; in response to receiving the registrationrequest, registering the bi-directional communications device as themobile bug by associating, based on the PIN in the registration request,the transmitting address included in the registration request with thereceiving address in the mapping table; receiving, by the server, anactivation request comprising the transmitting address of thebi-directional communications device registered as the mobile bug; andin response to receiving the activation request, transmitting, by theserver, instructions for: establishing a connection to the mobile bugthrough the receiving address to permit monitoring of the mobile bug;and disabling outgoing audio from the receiving address to the mobilebug on the connection.
 2. The method of claim 1, wherein generating thePIN further comprises: generating the PIN as a transmitting PIN forregistering the bi-directional communications device as the mobile bugand additionally generating a monitoring PIN for registering amonitoring device; and associating the monitoring PIN with the receivingaddress.
 3. The method of claim 2, wherein receiving the registrationrequest further comprises: identifying the PIN in the mapping table asthe transmitting PIN or the monitoring PIN; in response to identifyingthe PIN as the transmitting PIN, identifying the transmitting address ofthe bi-directional communications device as corresponding to the mobilebug; and associating the transmitting address of the mobile bug with thetransmitting PIN and the receiving address in the mapping table toidentify the transmitting address as corresponding to the mobile bug inthe mapping table.
 4. The method of claim 2, further comprising:receiving a second registration request, the second registration requestcomprising a second PIN and a second transmitting address of a secondbi-directional communications device; identifying the second PIN in themapping table as the transmitting PIN or the monitoring PIN; in responseto identifying the second PIN as the monitoring PIN, identifying thesecond transmitting address as corresponding to the monitoring device;and associating the second transmitting address of the monitoring devicewith the monitoring PIN and the receiving address in the mapping tableto identify the second transmitting address as corresponding to themonitoring device.
 5. The method of claim 4, further comprising, inresponse to receiving the activation request: identifying thetransmitting address of the monitoring device stored in association withthe receiving address in the mapping table, and transmittinginstructions for: establishing a second connection, the secondconnection established with the monitoring device through the receivingaddress to permit the monitoring device to monitor the mobile bug; andpassing audio received from the mobile bug on the first connectionestablished through the receiving address to the second connectionestablished with the monitoring device through the receiving address. 6.The method of claim 1, further comprising receiving from a relayconfigured to forward messages received from telephonic devices on themessage service: the registration request; and the activation request.7. The method of claim 6, wherein the relay receives the messages frombi-directional communications devices on a short message service.
 8. Themethod of claim 1, further comprising transmitting, to a relayconfigured to forward messages to bi-directional communications deviceson a short message service: a first message comprising the receivingaddress and the PIN in response to associating the receiving addresswith the PIN in the mapping table; and a second message comprising aregistration confirmation in response to associating the transmittingaddress of the mobile bug with the PIN and the receiving address in themapping table.
 9. The method of claim 1, further comprising providing abug module to the mobile bug, the bug module configured to interfacewith the bi-directional communications device and comprising computerprogram code for: receiving a transmitting address of a relay;intercepting messages received from the relay based on the transmittingaddress of the relay, the intercepted messages not appearing in a nativemessaging application; and suppressing notifications on the mobile bugfor intercepted messages.
 10. The method of claim 1, further comprisingproviding a bug module to the mobile bug, the bug module configured tointerface with the bi-directional communications device and comprisingcomputer program code for: receiving the receiving address; interceptingconnection requests from the receiving address, the interceptedconnection requests not appearing in a call log on the mobile bug;suppressing notifications on the mobile for intercepted connectionrequests from the receiving address; and automatically establishing aconnection with the receiving address in response to intercepting aconnection request.
 11. A system for configuring a bi-directionalcommunications device as a one-way transmitter (mobile bug), the systemcomprising: a server comprising one or more processors and anon-transitory computer-readable storage medium, the non-transitorycomputer-readable storage medium comprising instructions that whenexecuted cause the one or more processors to: provision, by the server,a virtual address as a receiving address; generate, by the server,without user input as to a unique personal identification number (PIN),the PIN for registering a bi-directional communications device as amobile bug, the generated PIN stored in association with the receivingaddress in a mapping table; receive, by the server, a registrationrequest comprising the PIN and a transmitting address of thebi-directional communications device to register the bi-directionalcommunications device as the mobile bug; in response to receiving theregistration request, register the bi-directional communications deviceas the mobile bug by associating, based on the PIN in the registrationrequest, the transmitting address included in the registration requestwith the receiving address in the mapping table; receive, by the server,an activation request comprising the transmitting address of thebi-directional communications device registered as the mobile bug; andin response to receiving the activation request, transmit, by theserver, instructions for: establishing a connection to the mobile bugthrough the receiving address to permit monitoring of the mobile bug;and disabling outgoing audio from the receiving address to the mobilebug on the connection.
 12. The system of claim 11, wherein, whengenerating the PIN, the one or more processors are further caused to:generate the PIN as a transmitting PIN for registering thebi-directional communications device as the mobile bug and additionallygenerating a monitoring PIN for registering a monitoring device; andassociate the monitoring PIN with the receiving address.
 13. The systemof claim 12, wherein, when receiving the registration request, the oneor more processors are further caused to: identify the PIN in themapping table as the transmitting PIN or the monitoring PIN; in responseto identifying the PIN as the transmitting PIN, identify thetransmitting address of the bi-directional communications device ascorresponding to the mobile bug; and associate the transmitting addressof the mobile bug with the transmitting PIN and the receiving address inthe mapping table to identify the transmitting address as correspondingto the mobile bug in the mapping table.
 14. The system of claim 12,wherein the one or more processors are further caused to: receive asecond registration request, the second registration request comprisinga second PIN and a second transmitting address of a secondbi-directional communications device; identify the second PIN in themapping table as the transmitting PIN or the monitoring PIN; in responseto identifying the second PIN as the monitoring PIN, identify the secondtransmitting address as corresponding to the monitoring device; andassociate the second transmitting address of the monitoring device withthe monitoring PIN and the receiving address in the mapping table toidentify the second transmitting address as corresponding to themonitoring device.
 15. The system of claim 14, wherein the one or moreprocessors are further caused to, in response to receiving theactivation request: identify the transmitting address of the monitoringdevice stored in association with the receiving address in the mappingtable, and transmitting instructions for: establish a second connection,the second connection established with the monitoring device through thereceiving address to permit the monitoring device to monitor the mobilebug; and pass audio received from the mobile bug on the first connectionestablished through the receiving address to the second connectionestablished with the monitoring device through the receiving address.16. The system of claim 11, wherein the one or more processors arefurther caused to receive, from a relay configured to forward messagesreceived from telephonic devices on the message service: theregistration request; and the activation request.
 17. The system ofclaim 16, wherein the relay receives the messages from bi-directionalcommunications devices on a short message service.
 18. The system ofclaim 11, wherein the one or more processors are further caused totransmit, to a relay configured to forward messages to bi-directionalcommunications devices on a short message service: a first messagecomprising the receiving address and the PIN in response to associatingthe receiving address with the PIN in the mapping table; and a secondmessage comprising a registration confirmation in response toassociating the transmitting address of the mobile bug with the PIN andthe receiving address in the mapping table.
 19. The system of claim 11,wherein the one or more processors are further caused to provide a bugmodule to the mobile bug, the bug module configured to interface withthe bi-directional communications device and comprising computer programcode for: receiving a transmitting address of a relay; interceptingmessages received from the relay based on the transmitting address ofthe relay, the intercepted messages not appearing in a native messagingapplication; and suppressing notifications on the mobile bug forintercepted messages.
 20. The system of claim 11, wherein the one ormore processors are further caused to provide a bug module to the mobilebug, the bug module configured to interface with the bi-directionalcommunications device and comprising computer program code for:receiving the receiving address; intercepting connection requests fromthe receiving address, the intercepted connection requests not appearingin a call log on the mobile bug; suppressing notifications on the mobilefor intercepted connection requests from the receiving address; andautomatically establishing a connection with the receiving address inresponse to intercepting a connection request.